|
|
|
|
|
|
|
This chapter is an overview of the anatomy of a complete Visual Basic system. In particular, it examines the different ways subsystems interact to augment application behavior, describing the interfacing between the Graphical User Interface and Database Access Subsystems, between the Reporting and Printing and Graphical User Interface Subsystems, between the Workgroup and User Security Subsystems, between the Database Access and Internal Application Manager Subsystems, and between the Internal Application Manager Subsystem and all the subsystems. You learned how to identify the need for other subsystems. Finally, the deployment of the Samsona Bank Teller System is carried out. |
|
|
|
|
|
|
|
|
For tomorrow's lesson, which is the last one, you go beyond technical details to understand how to make object-oriented programming in Visual Basic more successful in a commercial or corporate environment. That is, you learn how to round out your technical knowledge with advice on how to maximize your surroundings so that you can better concentrate on Visual Basic development and the power of Visual Basic. Focusing on programming rather than on politics or other stressful factors is very important in discovering and designing robust, lasting classes. |
|
|
|
|
|
|
|
|
Q True or False: An application is at its best when its expected behavior is compartmentalized into subsystems. Subsystems, in turn, are compartmentalized into classes. |
|
|
|
|
|
|
|
|
Q Do the Graphical User Interface Subsystem and the Database Access Subsystem always need to interact directly? |
|
|
|
|
|
|
|
|
A The Graphical User Interface Subsystem and the Database Access Subsystem typically don't need to communicate directly with one another. Data controls are an exception. |
|
|
|
|
|
|
|
|
Q What are the various data access mechanisms that the Database Access Subsystem encapsulates from the other subsystems in the application? |
|
|
|
|
|
|
|
|
A The Database Access Subsystem classes communicate with the database itself through any number of data access mechanisms, including Ado, Rdo, Dao, ODBC API, VBSQL (SQL Server DBLIB and SQLOLE objects), data controls, and third-party data access mechanisms such as Oracle Objects. |
|
|
|
|
|